home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_1
/
hang500.zip
/
HANGMAN.DOC
< prev
next >
Wrap
Text File
|
1992-04-02
|
10KB
|
226 lines
HANGMAN
a DOORware program by
Roland Haley
Copyright (C) 1992
using
DOORPCH v3.8
by
Raymond Clements
Copyright (C)1987-1991
Preface
---------
This is NOT meant to tell you how to setup DOORs on your BBS,
just how to setup DORPCH38 doors.
Support Shareware
-------------------
Thank you for obtaining this door program. Many hours of coding
have gone into its development. Like all shareware products,
You're encouraged to register this program if it meets your needs.
Supporting Shareware helps insure the future development of such
programs and will entitle you to support from their authors.
Environment variables
-----------------------
Two environment variables must be set in your AUTOEXEC.BAT file:
SET LIB=<drive:><path to DORPCH38.EXE> Note: ONLY the PATH!
Example: SET LIB=C:\MYLIB
The DORPCH38.EXE run-time library and DOORPCH.CFG files must then
be placed in this directory. I'd suggest a separate directory as
I do on my system and include it in your PATH statement.
SET DOORPCH=PCB This variable is required by prior versions
of DOORPCH, but not by DORPCH38.EXE.
For your convenience DOORPCH v3.8 also supports the following three
new variables:
%NODE% , %DRIVE% , and %DIRECTORY%
SET NODE=1 (ie. 1 , 2 , etc.)
SET DRIVE=C: (ie. C: , D: , etc.)
SET DIRECTORY=\BBS\ (ie. \PCB\ , \BBS\ , etc.)
These may be used to allow a single HANGMAN.CFG file for all nodes.
When using these variables please remember the combination of them
MUST form a valid DOS 'drive:\path\' pointing to the location of the
BBS interface file.
DOORPCH.KEY
-------------
DoorPch is released as a completely UNcrippled program. Upon
registering DoorPch you'll receive a DOORPCH.KEY file. This
file should be put in the 'SET LIB = ' directory along with the
DORPCH38.EXE and DOORPCH.CFG files. Upon exiting, all DOORs
using DoorPch v3.8 will then say 'This copy of DoorPch v3.8 is
registered to: ' and your BBS name, your name and your serial
number.
DOOR Setup
------------
Make a batch file to run the DOOR as described in your BBS
documentation.
@ECHO OFF
You may use the environmental variables to only require one
HANGMAN.CFG file for multiple nodes.
C:\BBS\DOOR.SYS <== The drive:\path\filename
of your BBS interface file
which is the same as
%DRIVE%%DIRECTORY%DOOR.SYS
using the above variables.
Haley's Comment BBS <== The name of your BBS.
Roland <== The SysOp's FIRST name.
Haley <== The SysOp's LAST name.
Your SysOp <== The name of the DOOR's donor.
20 <== Number of games allowed
D:\NEWS\0NEWS.TXT <== Drive:\Path\Name of bulletin
1000 <== number of lines to keep
Command-line parameters
-------------------------
This parameter may be used when starting a DOORPCH v3.8 DOOR.
/LOCAL <== Allows local usage of the DOOR as
the SysOp.
(ie. HANGMAN HANGMAN.CFG /LOCAL)
LIBRARIES
-----------
All DOORPCH v3.8 DOORs require the DORPCH38.EXE run-time library
and the Microsoft (R) QuickBASIC 3.0 run-time library, BRUN30.EXE,
be in your path. Your DOOR program may have come with these files
in the archive file. If they are not present, this DOOR program
WILL NOT RUN. You should contact the DOOR author if the files
are missing. You require one and only one version of these two
libraries for ALL DOORPCH v3.8 DOORware.
DOOR operation
----------------
When this DOOR is in operation you have complete control over the
caller. This DOOR was written using DOORPCH v3.8. The logic is
safe and every precaution has been taken to insure this code works
flawlessly. If it doesn't, please let us know. Many
function/operational keys are at your disposal:
F1 - Displays the version of DOORPCH compiled and linked
into the DOOR.
F2 - Displays a caller's Alias if one is used via the DOOR.
F3 - Toggles Local Music ON/OFF.
F4 - Toggles the Bell ON/OFF.
Value is returned to BBS when DOOR completes.
F5 - DOS Shell. Allows the SysOp to exit to DOS from inside
a DOOR.
F6 - Toggles the Graphics mode of the caller ON/OFF.
Value is returned to BBS when DOOR completes.
F7 - Toggle the caller alarm ON/OFF.
Value is returned to BBS when DOOR completes.
F8 - Involuntarily returns the caller to the BBS.
F9 - Toggles the display ON/OFF.
Value is returned to BBS when DOOR completes. Some doors
may force the display ON, but the original OFF value will
be returned to the BBS if this occurs.
F10 - Activates SysOp/Caller CHAT mode within the DOOR.
ESC - Deactivates CHAT mode. DOOR is resumed.
ALT-H - HELP key for lines 24/25 capabilities.
UP - Allows the SysOp to add additional time for the caller.
Value is returned to BBS when DOOR completes.
DN - Allows the SysOp to subtract time from the caller.
Value is returned to BBS when DOOR completes.
ALT-N - Some BBSs use SysOp next on control/indicator.
Value is returned to BBS when DOOR completes.
ALT-X - Some BBSs will exit after current caller completes their
session. Value is returned to BBS when DOOR completes.
Example: device = ANSI.SYS
--------------------------
DOORPCH uses this device driver for displaying all colors and
screen positioning to the local console. ANSI Color Graphics will
always be sent to the local console if you are using a color
monitor. If a caller is in non-graphics mode you will still see
colors if you have a color monitor. The reverse is also true.
If the caller is in graphics mode and the local console is a mono
monitor then colors will NOT be displayed to the local console.
BELL
------
DOORPCH logic will not allow a BELL to be sent to the local
console when the local screen is inactive (F9 OFF) or the caller
alarm is toggled off (F7 OFF). This, of course, assumes the
DOOR author follows the DOORPCH rules.
Errors
--------
All errors should recover and cause the DOOR program to exit
gracefully and return to the main system. All errors are logged
in the 'DOORPCH.ERR' file found in the 'SET; LIB =' directory. The
error number and line number are included with the date and time.
Errors will be either caused by the main module (the authors code,
contact him/her) or the DOORPCH sub (contact Raymond Clements).
It should NEVER cause the BBS to hang. If your BBS hangs, you are
requested to contact the appropriate party and report the error and
circumstances that caused it. Because we are using Microsoft's (c)
QuickBASIC 3.0 run-time routines, it is possible that BASIC will
detect a fatal error condition. As mentioned above, we have taken
every precaution, but simply cannot code for every error condition.
If the DOOR author follows all the rules, the DOOR should run without
error.
REGISTRATION
------------
To register this door, please read and fill out the ORDER.FRM which
is included in this ZIP.
HALEY'S COMMENT BBS
-----------------------
PCBoard v14.5a/E3
(519) 469-3028
(519) 469-3173
(519) 539-6851